Intelligent electronic footwear and control logic for automated pedestrian collision avoidance

ABSTRACT

Presented are intelligent electronic footwear with controller automated features, methods for making/using such footwear, and control systems for executing automated features of intelligent electronic footwear. An intelligent electronic shoe includes an upper that attaches to a user&#39;s foot, and a sole structure attached to the upper for supporting thereon the user&#39;s foot. A collision threat warning system, a detection tag, a wireless communications device, and a footwear controller are all mounted to the sole structure/upper. The detection tag receives a prompt signal from a transmitter-detector module and responsively transmits thereto a response signal. The footwear controller receives, through the wireless communications device, a pedestrian collision warning signal generated by the remote computing node responsive to the response signal. Responsively, the footwear controller transmits a command signal to the collision threat warning system to generate a visible, audible and/or tactile alert warning the user of an impending collision with a vehicle.

CLAIM OF PRIORITY AND CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/114,646, which was filed on Aug. 28, 2018, is now allowed, and claimsthe benefit of and priority to U.S. Provisional Patent Application No.62/678,796, which was filed on May 31, 2018, both of which areincorporated herein by reference in their respective entireties and forall purposes.

TECHNICAL FIELD

The present disclosure relates generally to wearable electronic devices.More specifically, aspects of this disclosure relate to systems,methods, and devices for enabling automated features of intelligentelectronic footwear and apparel.

BACKGROUND

Articles of footwear, such as shoes, boots, slippers, sandals, and thelike, are generally composed of two primary elements: an upper forsecuring the footwear to a user's foot; and a sole structure forproviding subjacent support for the foot. Uppers may be fabricated froma variety of materials—including textiles, foams, polymers, natural andsynthetic leathers, etc.—that are stitched or adhesively bonded togetherto form a shell or harness for securely receiving a foot. For sandalsand slippers, the upper may have an open toe or heel construction or maybe generally limited to a series of straps extending over the instepand, in some designs, around the ankle. Conversely, boot and shoedesigns incorporate a full upper with a closed toe and heel constructionand an ankle opening through a rear quarter portion that provides accessto the footwear's interior, facilitating entry and removal of the footinto and from the upper. A shoelace or strap may be utilized to securethe foot within the upper.

The sole structure is generally attached to a lower portion of theupper, positioned between the user's foot and the ground. In manyarticles of footwear, including athletic shoes, the sole structure is alayered construction that generally incorporates a comfort-enhancinginsole, an impact-mitigating midsole, and a surface-contacting outsole.The insole, which may be located partially or entirely within the upper,is a thin and compressible member that provides a contact surface forthe underside of the user's foot. By comparison, the midsole is mountedunderneath the insole, forming a middle layer of the sole structure. Inaddition to attenuating ground reaction forces, the midsole may help tocontrol foot motion and impart stability. Secured to the underside ofthe midsole is an outsole that forms the ground-contacting portion ofthe footwear and is usually fashioned from a durable and wear-resistantmaterial that includes features for improving traction.

SUMMARY

Presented herein are intelligent electronic footwear with attendantcontrol logic for enabling automated footwear capabilities, methods formaking and methods for using such footwear, and control systems forprovisioning automated features of intelligent electronic footwear. Byway of example, there is presented an Internet of Adaptive Apparel andFootwear (IoAAF) system that wirelessly communicates with an intelligentelectronic shoe (IES) to provision communication between the IES and amotor vehicle, i.e., footwear-to-vehicle (F2V) communications, or theIES and an intelligent transportation system, i.e.,footwear-to-infrastructure (F2I) communications. In a representativeimplementation, an IES is equipped with a detection tag, such as a radiofrequency (RF) transponder, that receives an incoming prompt signal.Prompt signals may be broadcast by a transmitter-detector module mountedto a stationary structure, such as a building, lamp post, or trafficsignal pole, or to a moving structure, such as a Society of AutomotiveEngineers (SAE) Levels 3, 4 or 5 autonomous vehicle. The IES detectiontag replies to this incoming signal, which may have an RF power with afirst frequency, by retransmitting the incoming signal as a transparentoutput signal, e.g., with an RF power having a second frequency. Thetransponder may be outfit with a frequency filter that limits incomingsignals to those with the first frequency, a frequency converter thatconverts the incoming signal into the transparent output signal, and anamplifier that intensifies the output signal based on the incomingsignal. Using vehicle-mounted or structure-mounted RFtransmitter-detector modules to sweep an upcoming or surrounding areafor response signals output by an IES transponder facilitates pedestriancollision avoidance by providing advance warning prior to field of viewrecognition.

By placing a detection tag on an IES and automating communicationbetween the IES detection tag and a complementary transmitter-detectormounted on a vehicle, street pole, etc., the networked IoAAF systemallows the connected parties to “see ahead” of an impending collision byeliminating the need for direct line-of-sight sensing and providesupcoming “awareness” before the IES is in close proximity to thevehicle. In effect, the IoAAF system architecture helps to eliminatefalse negatives caused by standard sensor hardware being unable toeffectively monitor pedestrians concealed at blind corners or behindother visual obstructions. Collision avoidance can be further enhancedby automating an audible, visible, and/or tactile warning to thepedestrian via the IES or by altering pedestrian flow through modulationof crosswalk signal timing. In addition to enabling pedestrian safetyrecognition, disclosed IoAAF systems can be employed in a manufacturingfacility, e.g., to prevent robot-borne injury to assembly line workers,in a storage facility, e.g., to avert collision between a worker and aforklift or automated guided vehicle (AGV), or at a road constructionsite, e.g., to protect constructions workers from passing vehicles.

For F2V and F2I applications, the IoAAF system can automatecommunication with the smart footwear/apparel to conduct a pedestriancollision threat assessment based on a myriad of available data. Forinstance, the F2I system may conduct a pedestrian collision threatassessment prior to line-of-sight between the moving object and IES userby aggregating, fusing, and analyzing: IES-generated user dynamics data(e.g., location, velocity, trajectory, accel./decel., etc.); userbehavioral data (e.g., historical behavior at particular corner ofintersection, historical behavior at intersections generally, historicalbehavior in current surrounding conditions, etc.); environmental data(e.g., intersection with red light vs. green light, residential vs.urban setting, inclement weather conditions vs. optimal drivingconditions); crowd-sourced data (dynamics and behavior of otherpedestrians near the IES user whom are also wearing intelligentfootwear/apparel). Interoperable component communication is typicallywireless and bi-directional, with data being delivered to and frominfrastructure components over an ad hoc network e.g., using dedicatedshort-range communication (DSRC). Traffic management supervision systemscan use IES, infrastructure, and vehicle data to set variable speedlimits and adjust traffic signal phase and timing.

To enable wireless communications between an IES and a remote computingnode, the IES may piggyback a communications session established by theuser's smartphone, handheld computing device, or other portableelectronic device with wireless communications capabilities.Alternatively, the IES may operate as a standalone device with aresident wireless communications device that is packaged within the shoestructure. Other peripheral hardware may include a resident controller,shortwave antenna, rechargeable battery, resident memory, SIM card,etc., all of which are housed inside the shoe structure. An IES may beequipped with a human-machine interface (HMI) that allows the user tointeract with the footwear and/or the IoAAF system. For instance, one ormore electroactive polymer (EAP) sensors may be woven into or formed aspatches mounted on the shoe structure and operable to receive userinputs that allow the user to control operational aspects of the IES.Likewise, any of the attendant operations for executing an automatedfootwear feature may be executed locally via the IES controller or maybe off-boarded in a distributing computing fashion for execution by thesmartphone, handheld computing device, IoAAF system, or any combinationthereof.

As yet a further option, execution of any one or more desired footwearfeatures may initially require security authentication of a user via theIES controller and/or an IoAAF system server computer. For instance, adistributed array of sensors within the shoe structure communicates withthe IES controller to perform biometric validation, such as confirming auser's weight (e.g., via pressure sensors), shoe size (e.g., via ElectroAdaptive Reactive Lacing (EARL)), toe print (e.g., via an opticalfingerprint sensor), gait profile, or other suitable method. As anextension of this concept, any of the foregoing sensing devices may beemployed as a binary (ON/OFF) switch to confirm the IES is actually on auser's foot when attempting to execute an automated feature.

Provisioning wireless data exchanges to facilitate execution of anautomated feature may require the IES be registered with the IoAAFsystem. For instance, a user may record an IES serial number with theIoAAF system, which will then issue a validation key to a personalaccount, e.g., a “digital locker” operating on the user's smartphone,tablet, PC, or laptop, to provide additional authentication.Registration may be completed manually, e.g., via the user, ordigitally, e.g., via a barcode or near-field communication (NFC) tag onthe shoe. A unique virtual shoe may be assigned to an IES and stored inthe digital locker; each virtual shoe may be backed by a blockchainsecurity technology designed to help guarantee uniqueness andauthenticity, such as a cryptographic hash function, a trustedtimestamp, correlating transaction data, etc. While described withreference to an article of footwear as a representative application forthe novel concepts presented herein, it is envisioned that many of thedisclosed options and features may be applied to other wearable apparel,including clothing, headgear, eyewear, wrist wear, neck wear, leg wear,and the like. It is also envisioned that the disclosed features beimplemented as part of an augmented reality (AR) device or system thatis operable to superimpose data, notifications, and other visualindicators to carry out any of the techniques and options presentedabove and below.

Aspects of the present disclosure are directed to networked controlsystems and attendant logic for executing automated footwear features.For instance, an intelligent electronic shoe system is presented thatincludes an article of footwear with an upper that attaches to a user'sfoot, and a sole structure that is attached to the upper and supportsthereon the user's foot. The sole structure includes an outsole thatdefines a bottom-most, ground-engaging surface of the footwear. The IESsystem also includes a collision threat warning system, a detection tag,and a wireless communications device, all of which are mounted to thesole structure and/or upper. The collision threat warning systemgenerates visible, audible, and/or tactile outputs in response toelectronic command signals. The detection tag receives one or moreprompt signals from a transmitter-detector module and, responsive to thereceived prompt signal, transmits one or more response signals to thetransmitter-detector module. The footwear controller, which may beresident to or remote from the footwear, is programmed to receive, fromthe remote computing node via the wireless communications device, apedestrian collision warning signal generated responsive to the IESdetection tag's response signal. In response to the received pedestriancollision warning signal, the footwear controller automaticallytransmits one or more command signals to the collision threat warningsystem to generate a predetermined visible, audible, and/or tactilealert designed to warn the user of an impending collision with a motorvehicle.

Additional aspects of this disclosure are directed to methods formanufacturing and methods for using any of the disclosed systems anddevices. In an example, a method is presented for operating anintelligent electronic shoe. This representative method includes, in anyorder and in any combination with any of the above or below disclosedfeatures and options: receiving, via a detection tag attached to thesole structure and/or upper of the IES, a prompt signal from atransmitter-detector module; transmitting, via the detection tagresponsive to receipt of the prompt signal, a response signal to thetransmitter-detector module; receiving, via a resident footwearcontroller through a wireless communications device both attached to thesole structure and/or upper, a pedestrian collision warning signalgenerated by a remote computing node responsive to the detection tag'sresponse signal; and transmitting, via the resident footwear controllerin response to the received pedestrian collision warning signal, acommand signal to a collision threat warning system attached to the solestructure and/or upper to generate a predetermined visible, audibleand/or tactile alert that is configured to warn the user of an impendingcollision with a motor vehicle.

For any of the disclosed systems, methods and devices, the detection tagmay include an RF transponder that is mounted to the sole structureand/or upper. In this instance, the prompt signal has a first RF powerwith a first frequency, whereas the response signal has a second RFpower with a second frequency that is distinct from the first frequency.For RF transponder applications, the prompt signal may include anembedded data set; the detection tag retransmits the embedded data setback to the transmitter-detector module in the response signal. The RFtransponder may be equipped with an RF antenna connected to a frequencyfilter. In this instance, the frequency filter is configured to rejectsignals having an RF power with a first frequency that is distinct fromthe first frequency. For at least some alternative configurations, thedetection tag includes an EAP sensor with a dielectric EAP elementmounted to the sole structure and/or upper. In this instance, the promptsignal is an electrical field that induces a physical state change inthe dielectric EAP element, and the response signal is generated by theuser reversing the physical state change of the dielectric EAP element.

For any of the disclosed systems, methods and devices, the footwearcontroller may be further programmed to transmit user position data anduser dynamics data through the wireless communications device to theremote computing node. The remote computing node thereafter transmits,and the footwear controller receives, a pedestrian collision threatvalue that is based on fusion of the user position data and userdynamics data. This pedestrian collision threat value is predictive ofintrusion of the user with respect to a vehicle location and predictedroute of the motor vehicle. The footwear controller may also transmit tothe remote computing node behavioral data that is indicative ofhistorical behavior of the user. In this instance, the pedestriancollision threat value is further based on fusion of the behavioral datawith the user position and user dynamics data. Calculation of thepedestrian collision threat value may also be based on fusion of thebehavioral data, user position data, and user dynamics data withcrowd-sourced data that is indicative of behavior of multipleindividuals in proximity to the user. As yet a further option, thepedestrian collision threat value may also be based on fusion of thebehavioral data, user position data, user dynamics data, andcrowd-sourced data with environmental data that is indicative of asurrounding environment of the user.

For any of the disclosed systems, methods and devices, the user may becarrying a portable electronic device, such as a smartphone or tabletcomputer. In this instance, the wireless communications device may beconfigured to wirelessly connect to the portable electronic device andthereby wirelessly communicate with the remote computing node. In someapplications, the remote computing node is a resident vehicle controllerof a motor vehicle. The footwear controller may be programmed totransmit user position data, user dynamics data and/or user behavioraldata through the wireless communications device to the resident vehiclecontroller. For other applications, the remote computing node may be acentral control unit of an intelligent traffic management system. Inthis instance, the footwear controller may be programmed to transmituser position data, user dynamics data and/or user behavioral data tothe central control unit via the wireless communications device.

For any of the disclosed systems, methods and devices, the collisionthreat warning system includes a haptic transducer that is attached tothe IES's sole structure and/or upper. In this example, the commandsignal causes the haptic transducer to generate a predetermined tactilealert designed to warn the user of the impending collision with themotor vehicle. The collision threat warning system may also oralternatively include an audio component that is attached to the solestructure and/or upper. In this instance, the command signal causes theaudio component to generate a predetermined audible alert that isconfigured to warn the user of the impending collision. Optionally, thecollision threat warning system may include a lighting element that isattached to the sole structure and/or upper. The command signal maycause the lighting element to generate a predetermined visible alertthat warns the user of the impending collision with the motor vehicle.

For any of the disclosed systems, methods and devices, the IES mayinclude a pressure sensor that is mounted to the sole structure andconfigured to detect a presence of a foot in the upper. In this example,the command signal may be transmitted to the collision threat warningsystem further in response to the detected presence of the foot in theupper. The IES may also include a shoelace that is attached to theupper, and a lace motor that is mounted inside the sole structure. Thislace motor is selectively actuable by the footwear controller totransition the shoelace between tensioned and untensioned states. Thefootwear controller may communicate with the lace motor to determinewhether the shoelace is in the tensioned or untensioned state. In thisinstance, the command signal may be transmitted to the collision threatwarning system further in response to the shoelace being in thetensioned state.

The above summary is not intended to represent every embodiment or everyaspect of the present disclosure. Rather, the foregoing summary merelyprovides an exemplification of some of the novel concepts and featuresset forth herein. The above features and advantages, and other featuresand attendant advantages of this disclosure, will be readily apparentfrom the following detailed description of illustrated examples andrepresentative modes for carrying out the present disclosure when takenin connection with the accompanying drawings and the appended claims.Moreover, this disclosure expressly includes any and all combinationsand subcombinations of the elements and features presented above andbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a lateral side-view illustration of a representativeintelligent electronic shoe with controller-automated footwear featuresin accordance with aspects of the present disclosure.

FIG. 2 is a partially schematic, bottom-view illustration of therepresentative intelligent electronic shoe of FIG. 1.

FIG. 3 is a partially schematic, perspective-view illustration of arepresentative user wearing a pair of the intelligent electronic shoesof FIGS. 1 and 2 during a wireless data exchange with a representativemotor vehicle to execute one or more automated footwear features as partof a pedestrian collision avoidance protocol.

FIG. 4 is an elevated perspective-view illustration of multiplerepresentative users wearing a pair of the intelligent electronic shoesof FIGS. 1 and 2 during a wireless data exchange with a representativeintelligent traffic management system to execute one or more automatedfootwear features.

FIG. 5 is a flowchart for an automated footwear feature protocol thatmay correspond to memory-stored instructions executed by resident orremote control-logic circuitry, programmable controller, or othercomputer-based device or network of devices in accord with aspects ofthe disclosed concepts.

The present disclosure is amenable to various modifications andalternative forms, and some representative embodiments have been shownby way of example in the drawings and will be described in detailherein. It should be understood, however, that the novel aspects of thisdisclosure are not limited to the particular forms illustrated in theabove-enumerated drawings. Rather, the disclosure is to cover allmodifications, equivalents, combinations, subcombinations, permutations,groupings, and alternatives falling within the scope of this disclosureas encompassed by the appended claims.

DETAILED DESCRIPTION

This disclosure is susceptible of embodiment in many different forms.There are shown in the drawings and will herein be described in detailrepresentative embodiments of the disclosure with the understanding thatthese representative examples are provided as an exemplification of thedisclosed principles, not limitations of the broad aspects of thedisclosure. To that extent, elements and limitations that are describedin the Abstract, Technical Field, Background, Summary, and DetailedDescription sections, but not explicitly set forth in the claims, shouldnot be incorporated into the claims, singly or collectively, byimplication, inference or otherwise.

For purposes of the present detailed description, unless specificallydisclaimed: the singular includes the plural and vice versa; the words“and” and “or” shall be both conjunctive and disjunctive; the words“any” and “all” shall both mean “any and all”; and the words “including”and “comprising” and “having” shall each mean “including withoutlimitation.” Moreover, words of approximation, such as “about,”“almost,” “substantially,” “approximately,” and the like, may be usedherein in the sense of “at, near, or nearly at,” or “within 0-5% of,” or“within acceptable manufacturing tolerances,” or any logical combinationthereof, for example. Lastly, directional adjectives and adverbs, suchas fore, aft, medial, lateral, proximal, distal, vertical, horizontal,front, back, left, right, etc., may be with respect to an article offootwear when worn on a user's foot and operatively oriented with aground-engaging portion of the sole structure seated on a flat surface,for example.

Referring now to the drawings, wherein like reference numbers refer tolike features throughout the several views, there is shown in FIG. 1 arepresentative article of footwear, which is designated generally at 10and portrayed herein for purposes of discussion as an athletic shoe or“sneaker.” The illustrated footwear 10—also referred to herein as“intelligent electronic shoe” or “IES” for brevity—is merely anexemplary application with which novel aspects and features of thisdisclosure may be practiced. In the same vein, implementation of thepresent concepts for a wearable electronic device that is worn on ahuman's foot should also be appreciated as a representative applicationof the concepts disclosed herein. It will therefore be understood thataspects and features of this disclosure may be integrated into otherfootwear designs and may be incorporated into any logically relevanttype of wearable electronic device worn on any part of the body. As usedherein, the terms “shoe” and “footwear,” including permutations thereof,may be used interchangeably and synonymously to reference any relevanttype of garment worn on a foot. Lastly, features presented in thedrawings are not necessarily to scale and are provided purely forinstructional purposes. Thus, the specific and relative dimensions shownin the drawings are not to be construed as limiting.

The representative article of footwear 10 is generally depicted in FIGS.1 and 2 as a bipartite construction that is primarily composed of afoot-receiving upper 12 mounted on top of a subjacent sole structure 14.For ease of reference, footwear 10 may be divided into three anatomicalregions: a forefoot region R_(FF), a midfoot region R_(MF), and ahindfoot (heel) region R_(HF), as shown in FIG. 2. Footwear 10 may alsobe divided along a vertical plane into a lateral segment S_(LA)—a distalhalf of the shoe 10 farthest from the sagittal plane of the humanbody—and a medial segment S_(ME)—a proximal half of the shoe 10 closestto the sagittal plane of the human body. In accordance with recognizedanatomical classification, the forefoot region R_(FF) is located at thefront of the footwear 10 and generally corresponds with the phalanges(toes), metatarsals, and any interconnecting joints thereof. Interposedbetween the forefoot and hindfoot regions R_(FF) and R_(HF) is themidfoot region R_(MF), which generally corresponds with the cuneiform,navicular and cuboid bones (i.e., the arch area of the foot). Heelregion R_(HF), in contrast, is located at the rear of the footwear 10and generally corresponds with the talus and calcaneus bones. Bothlateral and medial segments S_(LA) and S_(ME) of the footwear 10 extendthrough all three anatomical regions R_(FF), R_(MF), R_(HF), and eachcorresponds to a respective transverse side of the footwear 10. Whileonly a single shoe 10 for a left foot of a user is shown in FIGS. 1 and2, a mirrored, substantially identical counterpart for a right foot of auser may be provided, as shown in FIG. 3. Recognizably, the shape, size,material composition, and method of manufacture of the shoe 10 may bevaried, singly or collectively, to accommodate practically anyconventional or nonconventional application.

With reference again to FIG. 1, the upper 12 is depicted as having aclosed toe and heel configuration that is generally defined by threeadjoining sections: a toe box 12A that covers and protects the toes, avamp 12B located aft of the toe box 12A and extending around the laceeyelets 16 and tongue 18, and a rear quarter 12C positioned aft of thevamp 12B and includes the rear and sides of the upper 12 that covers theheel. The upper 12 portion of the footwear 10 may be fabricated from anyone or combination of a variety of materials, such as textiles, foams,polymers, natural and synthetic leathers, etc., that are stitched,adhesively bonded, or welded together to form an interior void forcomfortably receiving a foot. The individual material elements of theupper 12 may be selected and located with respect to the footwear 10 inorder to impart desired properties of durability, air-permeability,wear-resistance, flexibility, and comfort, for example. An ankle opening15 in the rear quarter 12C of the upper 12 provides access to theinterior of the shoe 10. A shoelace 20, strap, buckle, or otherconventional mechanism may be utilized to modify the girth of the upper12 to more securely retain the foot within the interior of the shoe 10as well as to facilitate entry and removal of the foot from the upper12. Shoelace 20 may be threaded through a series of eyelets in the upper12; the tongue 18 may extend between the lace 20 and the interior voidof the upper 12.

Sole structure 14 is rigidly secured to the upper 12 such that the solestructure 14 extends between the upper 12 and a support surface uponwhich a user stands (e.g., the sidewalk G_(S1) illustrated in FIG. 3).In effect, the sole structure 14 functions as an intermediate supportplatform that separates the user's foot from the ground. In addition toattenuating ground reaction forces and providing cushioning for thefoot, sole structure 14 of FIGS. 1 and 2 may provide traction, impartstability, and help to limit various foot motions, such as inadvertentfoot inversion and eversion. In accordance with the illustrated example,the sole structure 14 is fabricated as a sandwich structure with atop-most insole 22, an intermediate midsole 24, and a bottom-mostoutsole 26. Insole 22 is shown located partially within the interiorvoid of the footwear 10, firmly secured to a lower portion of the upper12, such that the insole 22 is located adjacent a plantar surface of thefoot. Underneath the insole 22 is a midsole 24 that incorporates one ormore materials or embedded elements that enhance the comfort,performance, and/or ground-reaction-force attenuation properties offootwear 10. These elements and materials may include, individually orin any combination, a polymer foam material, such as polyurethane orethylvinylacetate (EVA), filler materials, moderators, air-filledbladders, plates, lasting elements, or motion control members. Outsole26, which may be absent in some configurations of footwear 10, issecured to a lower surface of the midsole 24. The outsole 26 may beformed from a rubber material that provides a durable and wear-resistantsurface for engaging the ground. In addition, outsole 26 may also betextured to enhance the traction (i.e., friction) properties betweenfootwear 10 and the underlying support surface.

FIG. 3 is a partially schematic illustration of an exemplary IES datanetwork and communications system, designated generally as 30, forprovisioning wireless data exchanges to execute one or more automatedfootwear features for a pair of intelligent electronic shoes 10 worn bya user or client 11. While illustrating a single user 11 communicatingover the IES system 30 with a single motor vehicle 32, it is envisionedthat any number of users may communicate with any number of motorvehicles or other remote computing nodes that are suitably equipped forwirelessly exchanging information and data. One or both IES 10 of FIG. 3communicatively couples to a remote host system 34 or a cloud computingsystem 36 via a wireless communications network 38. Wireless dataexchanges between the IES 10 and IES system 30 may be conducteddirectly—in configurations in which the IES 10 is equipped as astandalone device—or indirectly—by pairing and piggy backing the IES 10onto a smartphone 40, smartwatch 42, wireless fidelity (WiFi) node, orother suitable device. In this regard, the IES 10 may communicatedirectly with the motor vehicle 32, e.g., via a short-range wirelesscommunication device (e.g., a BLUETOOTH® unit or near fieldcommunication (NFC) transceiver), a dedicated short-range communications(DSRC) component, a radio antenna, etc. Only select components of theIES 10 and IES system 30 are shown and will be described in detailherein. Nevertheless, the systems and devices discussed herein caninclude numerous additional and alternative features, and otheravailable hardware and well-known peripheral components, for example,for carrying out the various methods and functions disclosed herein.

With continuing reference to FIG. 3, the host system 34 may beimplemented as a high-speed server computing device or a mainframecomputer capable of handling bulk data processing, resource planning,and transaction processing. For instance, the host system 34 may operateas the host in a client-server interface for conducting any necessarydata exchanges and communications with one or more “third party” serversto complete a particular transaction. The cloud computing system 36, onthe other hand, may operate as middleware for IoT (Internet of Things),WoT (Web of Things), Internet of Adaptive Apparel and Footwear (IoAAF),and/or M2M (machine-to-machine) services, connecting an assortment ofheterogeneous electronic devices with a service-oriented architecture(SOA) via a data network. As an example, cloud computing system 36 maybe implemented as a middleware node to provide different functions fordynamically onboarding heterogeneous devices, multiplexing data fromeach of these devices, and routing the data through reconfigurableprocessing logic for processing and transmission to one or moredestination applications. Network 38 may be any available type ofnetwork, including a combination of public distributed computingnetworks (e.g., Internet) and secured private networks (e.g., local areanetwork, wide area network, virtual private network). It may alsoinclude wireless and wireline transmission systems (e.g., satellite,cellular network, terrestrial networks, etc.). In at least some aspects,most if not all data transaction functions carried out by the IES 10 maybe conducted over a wireless network, such as a wireless local areanetwork (WLAN) or cellular data network, to ensure freedom of movementof the user 11 and IES 10.

Footwear 10 is equipped with an assortment of embedded electronichardware to operate as a hands-free, rechargeable, and intelligentwearable electronic device. The various electronic components of the IES10 are governed by one or more electronic controller devices, such as aresident footwear controller 44 (FIG. 2) that is packaged inside thesole structure 14 of footwear 10. The footwear controller 44 maycomprise any one or various combinations of one or more of: a logiccircuit, a dedicated control module, an electronic control unit, aprocessor, an application specific integrated circuit, or any suitableintegrated circuit device, whether resident, remote or a combination ofboth. By way of example, the footwear controller 44 may include aplurality of microprocessors including a master processor, a slaveprocessor, and a secondary or parallel processor. Controller 44, as usedherein, may comprise any combination of hardware, software, and/orfirmware disposed inside and/or outside of the shoe structure of the IES10 that is configured to communicate with and/or control the transfer ofdata between the IES 10 and a bus, computer, processor, device, service,and/or network. The footwear controller 44 is generally operable toexecute any or all of the various computer program products, software,applications, algorithms, methods and/or other processes disclosedherein. Routines may be executed in real-time, continuously,systematically, sporadically and/or at regular intervals, for example,each 100 microseconds, 3.125, 6.25, 12.5, 25 and 100 milliseconds, etc.,during ongoing use or operation of the controller 44.

Footwear controller 44 may include or may communicate with a resident orremote memory device, such as a resident footwear memory 46 that ispackaged inside the sole structure 14 of footwear 10. Resident footwearmemory 46 may comprise semiconductor memory, including volatile memory(e.g., a random-access memory (RAM) or multiple RAM) and non-volatilememory (e.g., read only memory (ROM) or an EEPROM), magnetic-diskstorage media, optical storage media, flash memory, etc. Long-rangecommunication capabilities with remote networked devices may be providedvia one or more or all of a cellular network chipset/component, asatellite service chipset/component, or a wireless modem orchipset/component, all of which are collectively represented at 48 inFIG. 2. Close-range wireless connectivity may be provided via aBLUETOOTH® transceiver, a radio-frequency identification (RFID) tag, anNFC device, a DSRC component, and/or a radio antenna, all of which arecollectively represented at 50. A resident power supply, such as alithium ion battery 52 with plug-in or cable-free (induction orresonance) rechargeable capabilities, may be embedded within upper 12 orsole structure 14 of the footwear 10. Wireless communications may befurther facilitated through implementation of a BLUETOOTH Low Energy(BLE), category (CAT) M1 or CAT-NB1 wireless interface. The variouscommunications devices described above may be configured to exchangedata between devices as part of a systematic or periodic beacon messagethat is broadcast in a footwear-to-vehicle (F2V) information exchange, afootwear-to-everything (F2X) information exchange, e.g.,footwear-to-infrastructure (F2I), footwear-to-pedestrian (F2P), orfootwear-to-footwear (F2F).

Location and movement of the IES 10 and, thus, the user 11 may betracked via a location tracking device 54, which can reside inside thesole structure 14 or the upper 12. Location can be determined through asatellite-based global positioning system (GPS) or other suitablenavigation system. In an example, a GPS system may monitor the locationof a person, a motor vehicle or other target object on earth using acollaborating group of orbiting GPS satellites the communicate with asuitable GPS transceiver to thereby generate, in real-time, atime-stamped series of data points. In addition to providing datarelating to absolute latitudinal and absolute longitudinal positioncoordinates of a GPS receiver borne by a target object, data providedvia the GPS system may be adapted and used to provide informationregarding elapsed time during execution of a designated operation, atotal distance moved, an elevation or altitude at a specific location,an elevation change within a designated window of time, a movementdirection, a movement speed, and the like. Aggregated sets of theforegoing GPS data may be used by the resident footwear controller 44 toestimate a predicted route of the user 11. GPS system data, singly andcollectively, may be used to supplement and optionally to calibrateaccelerometer-based or other pedometer-based speed and distance data. Tothis end, information collected by the GPS satellite system may be usedto generate correction factors and/or calibration parameters for use bythe IES 10 to help ensure accurate sensor data and, thus, optimal systemoperation.

Even without a GPS receiver, the IES 10 can determine location andmovement information through cooperation with a cellular system througha process known as “trilateration.” A cellular system's towers and basestations communicate radio signals and are arranged into a network ofcells. Cellular devices, such as IES 10, may be equipped with low-powertransmitters for communicating with the nearest tower, base station,router, or access point. As a user moves with the IES 10, e.g., from onecell to another, the base stations monitor the strength of thetransmitter's signal. When the IES 10 moves toward the edge of one cell,the transmitter signal strength diminishes for a current tower. At thesame time, the base station in the approaching cell detects a strengthincrease in the signal. As the user moves into a new cell, the towerstransfer the signal from one to the next. Resident footwear controller44 can determine the location of the IES 10 based on measurements of thetransmitter signals, such as the angle of approach to the cell tower(s),the respective time it takes for individual signals to travel tomultiple towers, and the respective strength of each signal when itreaches a corresponding tower. According to other aspects of the presentconcepts, one or more movement sensing devices may be integrated intothe shoe structure to determine dynamic movement (e.g., translation,rotation, velocity, acceleration, etc.) of the IES 10 with respect to anestablished datum or reference (e.g., position, spatial orientation,reaction, force, velocity, acceleration, electrical contact, etc.) aboutor along one or more axes.

With collective reference to FIGS. 1 and 2, article of footwear 10 maybe equipped with a resident lighting system 56 with one or more lightingdevices governed by footwear controller 44 to selectively illuminate theshoe structure and surrounding areas thereof. Different types oflighting devices may be employed by the lighting system 56, includinglight emitting diodes (LEDs), electroluminescent panels (ELP), compactflorescent lamps (CFL), high intensity discharge lamps, flexible andinflexible organic LED displays, flat-panel liquid-crystal displays(LCD), as well as other available types of lighting elements. Any numberof lighting devices may be disposed on any portion of shoe 10; as shown,a first lighting device 58 is packaged inside the sole structure 14,located within the midfoot region R_(MF) of the footwear 10. Firstlighting device 58 is positioned immediately adjacent a window 60(FIG. 1) that seals off a frame aperture extending through a peripheralwall of the sole structure 14 on the lateral side of the shoe 10. Thislighting device 58 may be operated in an illuminated or “ON” state, anon-illuminated or “OFF” state, a series of illumination intensities(e.g., low, medium and high light outputs), an assortment of colors,and/or an assortment of illumination patterns. With this arrangement,the first lighting device 58 selectively illuminates a portion of upper12, a portion of the sole 14, and a portion of the ground surfaceGs/adjacent the IES 10.

With reference now to the flow chart of FIG. 5, an improved method orcontrol strategy for executing an automated feature, such as thefootwear features illustrated in FIG. 3, for a wearable electronicdevice, such as IES 10 of FIGS. 1 and 2, is generally described at 100in accordance with aspects of the present disclosure. Some or all of theoperations illustrated in FIG. 5 and described in further detail belowmay be representative of an algorithm that corresponds toprocessor-executable instructions that may be stored, for example, inmain or auxiliary or remote memory, and executed, for example, by aresident or remote controller, central processing unit (CPU), controllogic circuit, or other module or device, to perform any or all of theabove or below described functions associated with the disclosedconcepts. It should be recognized that the order of execution of theillustrated operation blocks may be changed, additional blocks may beadded, and some of the blocks described may be modified, combined, oreliminated.

Method 100 begins at terminal block 101 with processor-executableinstructions for a programmable controller or control module orsimilarly suitable processor, such as resident footwear controller 44 orFIG. 2, to call up an initialization procedure for a protocol to governoperation of a wearable electronic device, such as IES 10 of FIG. 1.This routine may be called-up and executed in real-time, continuously,systematically, sporadically, and/or at regular intervals, etc., duringuse of the intelligent electronic shoe 10. With reference to the IESdata network and communications system 30 architecture of FIG. 3, as arepresentative implementation of the methodology set forth in FIG. 5,the initialization procedure at block 101 may be automatically commencedeach time the user 11 approaches a roadway or roadway intersection 13,each time the user 11 approaches or is approached by a vehicle 32, oreach time the user 11 is within detectable proximity to a movingtransmitter-detector module 70 (e.g., mounted to the vehicle 32) or astationary transmitter-detector module 72 (e.g., mounted to a crosswalksignal post 74). Utilizing a portable electronic device, such assmartphone 40, smartwatch 42, the user 11 may launch a dedicated mobileapplication or a web-based applet that collaborates with an intelligenttransportation system (e.g., represented by remote host system 34)through an IoAAF middleware node (e.g., represented by cloud computingsystem 36) to monitor the user 11 as part of a pedestrian collisionavoidance procedure. The example illustrated in FIG. 3 portrays asingular pedestrian—a female runner—avoiding injury resulting from anaccident with a singular automobile—an SAE Level 3, 4 or 5 autonomousvehicle—at the intersection of urban roadway. However, it is envisionedthat the IES system 30 monitor and protect any number and type of userfrom any number and type of vehicle or object operating in any logicallyrelevant environment.

To enhance security, interaction between the IES 10 and IES system 30can be enabled by an authentication process at predefined process block103. Authentication may be performed by a primary or secondary sourcethat confirms proper activation of a wearable electronic device and/or avalid identity of the device's user. Upon manual entry of useridentification information, such as a password, PIN number, credit cardnumber, personal information, biometric data, predefined key sequences,etc., the user may be permitted to access a personal account, e.g., a“digital locker” operating on the user's smartphone 40 with a NIKE+®Connect software application and registered with the IoAAF middlewarenode. Thus, data exchanges can be enabled by, for example, a combinationof personal identification input (e.g., mother's maiden name, socialsecurity number, etc.) with a secret PIN number (e.g., six oreight-digit code), or a combination of a password (e.g., created by theuser 11) and a corresponding PIN number (e.g., issued by the host system34), or a combination of a credit card input with secret PIN number.Additionally or alternatively, a barcode, RFID tag, or NFC tag may beimprinted on or attached to the IES 10 shoe structure, and configured tocommunicate a security authentication code to the IES system 30. Otherestablished authentication and security techniques, including blockchaincryptographic technology, can be utilized to prevent unauthorized accessto a user's account, for example, to minimize an impact of unsanctionedaccess to a user's account, or to prevent unauthorized access topersonal information or funds accessible via a user's account.

As an alternative or supplemental option to manually enteringidentification information at predefined process block 103, securityauthentication of the user 11 may be automated by the resident footwearcontroller 44. By way of non-limiting example, a pressure sensor 62,which may be in the nature of a binary contact-type sensor switch, maybe attached to the footwear 10 (e.g., embedded within the midsole 24 ofthe sole structure 14). This pressure sensor 62 detects a calibratedminimum load on the insole 22 and thereby establishes the presence of afoot in the upper 12. Any future automated features of the IES 10 mayfirst require the controller 44 confirm, via command prompt to thebinary pressure sensor 62, that a foot is present in the upper 12 and,thus, the footwear 10 is in use before transmitting a command signal toinitiate an automated operation. While only a single sensor isillustrated in FIG. 2, it is envisioned that the IES 10 may be equippedwith a distributed array of sensors, including pressure, temperature,moisture, and/or shoe dynamics sensors, packaged at discrete locationsthroughout the shoe structure. In the same vein, foot presence sensing(FPS) may be determined via a variety of available sensing technologies,including capacitance, magnetic, etc. Additional information regardingfoot presence sensing can be found, for example, in U.S. PatentApplication Publication Nos. 2017/0265584 A1 and 2017/0265594 A1, toSteven H. Walker, et al., both of which are incorporated herein byreference in their respective entireties and for all purposes.

In addition to functioning as a binary (ON/OFF) switch, the pressuresensor 62 may take on a multi-modal sensor configuration (e.g., apolyurethane dielectric capacitive biofeedback sensor) that detects anyof assorted biometric parameters, such as the magnitude of an appliedpressure generated by a foot in the upper 12, and outputs one or moresignals indicative thereof. These sensor signals may be passed from thepressure sensor 62 to the resident footwear controller 44, which thenaggregates, filters and processes the received data to calculate acurrent user weight. The calculated current user weight for theindividual presently using the IES 10 is compared to a previouslyvalidated, memory-stored user weight (e.g., authenticated to aregistered user of an existing personal account). In so doing, thefootwear controller 44 can determine if the current user weight is equalto or within a predetermined threshold range of the validated userweight. Once the current user is authenticated to the validated user,the resident footwear controller 44 is enabled to transmit commandsignals to one or more subsystems within the footwear 10 to automate afeature thereof.

Automated security authentication of a user may be achieved throughother available techniques, as part of predefined process block 103,including cross-referencing characteristics of a current user's footwith previously validated characteristics of an authenticated user'sfoot. For instance, the representative IES 10 of FIG. 2 is shownfabricated with a motorized lacing system utilizing a lace motor (M) 64that is mounted to the footwear 10 and is selectively actuable totransition the shoelace 20 back-and-forth between an untensioned(loosened) state and one or more tensioned (tightened) states. Lacemotor 64 may be in the nature of a two-way DC electric worm-gear motorthat is housed inside the sole structure 14 and controlled by theresident footwear controller 44. Activation of the lace motor 64 may beinitiated via a manually-activated switch built into the shoe structureor softkey activation through an app on the user's smartphone 40 orsmartwatch 42. Control commands may include, but are certainly notlimited to, incremental tighten, incremental loosen, open/fully loosen,store “preferred” tension, and recall/restore tension. Additionalinformation pertaining to motorized shoelace tensioning systems can befound, for example, in U.S. Pat. No. 9,365,387 B2, which is incorporatedherein by reference in its entirety and for all purposes.

Motor control of lace motor 64 may be automated via the residentfootwear controller 44, for example, in response to a sensor signal frompressure sensor 62 indicating that a foot has been placed inside theupper 12. Shoelace tension may be actively modulated through governedoperation of the lace motor 64 by the controller 44 during use of theIES 10, e.g., to better retain the foot in response to dynamic usermovement. In at least some embodiments, an H-bridge mechanism isemployed to measure motor current; measured current is provided as aninput to footwear controller 44. Resident footwear memory 46 stores alookup table with a list of calibrated currents each of which is knownto correspond to a certain lace tension position. By checking a measuredmotor current against a calibrated current logged in the lookup table,the footwear controller 44 may ascertain the current tension position ofthe shoelace 20. The foregoing functions, as well as any other logicallyrelevant option or feature disclosed herein, may be applied toalternative types of wearable apparel, including clothing, headgear,eyewear, wrist wear, neck wear, leg wear, undergarments, and the like.Moreover, the lace motor 64 may be adapted to automate the tensioningand loosening of straps, latches, cables and other commerciallyavailable mechanisms for fastening shoes.

Similar to the pressure sensor 62 discussed above, the lace motor 64 maydouble as a binary (ON/OFF) switch that effectively enables and disablesautomated features of the IES 10. That is, the resident footwearcontroller 44, prior to executing an automated feature, may communicatewith the lace motor 64 to determine whether the shoelace 20 is in atensioned or untensioned state. If the latter, all automated featuresmay be disabled by the resident footwear controller 44 to prevent theinadvertent initiation of an automated feature while the IES 10 is notin use, for example. Conversely, upon determination that the lace 20 isin a tensioned state, the footwear controller 44 is permitted totransmit automation command signals.

During operation of the lace motor 64, the shoelace 20 may be placed inany one of multiple discrete, tensioned positions to accommodate feetwith differing girths or users with different tension preferences. Alace sensor, which may be built into the lace motor 64 or packaged inthe sole structure 14 or upper 12, may be employed to detect a currenttensioned position of the lace 20 for a given user. Alternatively,real-time tracking of a position of an output shaft (e.g., a worm gear)of the two-way electric lace motor 64 or a position of a designatedsection of the lace 20 (e.g., a lace spool mated with the motor's wormgear) may be used to determine lace position. Upon tensioning of thelace 20, the resident footwear controller 44 communicates with the lacemotor 64 and/or lace sensor to identify a current tensioned position ofthe lace 20 for a current user. This current tensioned position iscompared to a previously validated, memory-stored lace tensionedposition (e.g., authenticated to a registered user of an existingpersonal account). Through this comparison, the footwear controller 44can determine if the current tensioned position is equal to or within apredetermined threshold range of the validated tensioned position. Afterauthenticating the current user to the validated user, command signalsmay be transmitted via the resident footwear controller 44 to one ormore subsystems within the footwear 10 to automate a feature thereof.

Upon completion of the authentication procedure set forth in predefinedprocess block 103, the method 100 of FIG. 5 proceeds to input/outputblock 105 with processor-executable instructions to retrieve sufficientdata to track the motion of a wearable electronic device and a remotecomputing node that are moving with respect to each other. In accordwith the illustrated example of FIG. 3, the IES 10 may receive, eitherdirectly or through cooperative operation with the smartphone 40 orsmartwatch 42, location data from the remote host system 34 and/or cloudcomputing system 36 that is indicative of a current location andvelocity of the user 11 and a current location and velocity of the motorvehicle 32. User movement can also, or alternatively, be tracked througha dedicated mobile app or a route planning app running on the user'ssmartphone 40. Location and movement of the IES 10 and, thus, the user11 can also be determined, for example, through a satellite-based GPSnavigation system transceiver built into the upper 12 or sole structure14. A back-office intermediary server, such as cloud computing system 36operating as a middleware node, tracks in real-time the location andmovement of the vehicle 32, e.g., either through an on-boardtransmission device or through an app on the driver's personal computingdevice.

Another technique for ascertaining a user's location and attendantdynamics employs a detection tag 78 that is borne by the user 11 andcommunicates with a transmitter-detector module 70, 72 that is mountedto a nearby structure or on a nearby moving object. In accord with therepresentative application presented in FIGS. 1 and 3, the detection tag78 is embodied as a passive or active radio frequency (RF) transponderthat is mounted to an exterior surface of the sole structure 14. The RFtransponder 78 of FIG. 1 includes an omnidirectional (Type I) RF antennacoil 80 that is fabricated with an electrically conductive material andis shaped to receive and transmit signals in the form of electromagneticradiation waves. An RF frequency filter 82, which may be in the natureof a lumped-element Butterworth filter, is electrically connected to theRF antenna 80 and designed for bandpass operability to allow the passingof only those signals that have an RF power with a calibrated (first)frequency or are within a calibrated (first) frequency range. As anotheroption, the frequency filter 82 may provide band-stop functionality thatattenuates and denies the passing of all signals that have an RF powerwith an undesired frequency or a frequency within any one or moreundesired frequency bands, namely outside the calibrated (first)frequency range. An optional dielectric cover 84 is placed over the RFantenna 80, frequency filter 82, and attendant detection tag electronicsto protect the componentry and increase performance as an RFtransponder. Signal exchanges may be routed through a system packetinterface (SPI) interface and general-purpose input/outputs (GPIOs).Frequency and phase-tunable signal output may be provided through aphase lock loop (PLL) or direct digital synthesis (DDS) synthesizer,harmonic mixer, and PLL or DDS synthesizer-based local oscillator.

As the user 11 approaches the roadway intersection 13 of FIG. 3, thedetection tag 78 (FIG. 1) receives a frequency swept prompt signal S_(P)or “ping” emitted at regular intervals by a moving transmitter-detectormodule 70, which may be packaged proximate the front end of the vehicle32, or a stationary transmitter-detector module 72, which may be hung ona crosswalk signal post 74, a building wall, or similarly suitableimmobile structure. For applications in which the detection tag 78 iscomposed of a passive RF transponder, the transmitter-detector module70, 72 may broadcast the prompt signal S_(P) in a repeating orsubstantially continuous manner. Conversely, for active RF transponderimplementations, the incoming prompt signal S_(P) may be emitted inanswer to a callback signal broadcast by the detection tag 78 in arepeating or substantially continuous manner. The prompt signal S_(P) isan electromagnetic field wave that has a predetermined (first) RF powerlevel with a standardized (first) downlink frequency. In addition, theprompt signal S_(P) contains an embedded data set with encoded, uniqueinformation (e.g., transmitter ID, interrogation code, timestamp, etc.).Data can be superimposed over the swept carrier wave in a narrowbandsystem to help reduce bandwidth overhead that some implementations maycreate. It is to be noted that a reverse situation is also possible,where the detection tag 78 broadcasts and the module 70 accepts andretransmits prompt signal S_(P).

Upon receipt of this prompt signal S_(P), the detection tag 78responsively processes and retransmits the signal S_(P) back to thetransmitter-detector module 70, 72 as an outgoing response signal S_(R).The response signal S_(R) is an electromagnetic field wave that has adistinguishable (second) RF power with a complementary (second) uplinkfrequency that is distinct from the first frequency. The detection tag78 may be equipped with an RF frequency converter to modulate theincoming prompt signal S_(P) (e.g., by frequency multiplication of theincoming signal), and an RF signal amplifier that intensifies theresponse signal S_(R), based on the incoming prompt signal S_(P), priorto transmission of the signal S_(R) to the transmitter-detector module70, 72. To help ensure that the transmitter-detector module 70, 72recognizes the detection tag 78, the response signal S_(R) parrots atleast a portion of the prompt signal's S_(P) embedded data back to thetransmitter-detector module 70, 72. In order to minimize onboard powerusage, the detection tag 78 may operate in two modes: an idle mode andan active mode. When idling, the detection tag 78 is generally dormantand, thus, does not draw power from the resident power supply 52 or anoff-board power source. By comparison, when active, the detection tag 78temporarily extracts power from the resident power supply 52 or ispowered by the incoming prompt signal S_(P). As such, the detection tag78 does not transmit a transparent output signal unless and until anincoming signal with RF power of a predetermined frequency is received.

The intelligent electronic shoe 10 of FIGS. 1-3 may employ alternativemeans for exchanging data with the IES system 30 and motor vehicle 32 aspart of executing the pedestrian collision threat assessment. Ratherthan using an RF transponder, the detection tag 78 may be fabricatedwith one or more electroactive polymer (EAP) sensors, each of which hasa discrete dielectric EAP element mounted to the sole structure 14 orupper 12. In accord with this example, the incoming prompt signal S_(P)is an electrical field that generates a current with sufficient voltageto induce a physical state change (e.g., an arcing or expansion) of theimplanted dielectric EAP element. Through normal use of the IES 10, theuser 11 will unknowingly reverse the physical state change of the EAPsensor, e.g., by flattening or compressing the dielectric EAP elementwith their foot. In so doing, the EAP sensor will generate an electriccurrent that causes a response signal S_(R) to be output by the IES 10.It is also envisioned that the IES 10 may be enabled to communicatedirectly with the vehicle 32, e.g., through a device-to-device wirelessad hoc network (WANET), rather than redirecting all data through the IESsystem 30 or other preexisting wireless access point(s).

With reference again to FIG. 5, the method 100 continues to processblock 107 with processor-executable instructions for transmitting orreceiving a pedestrian collision warning signal that is generatedresponsive to transmission of a response signal S_(R) that indicates auser may enter or obstruct a roadway in a manner that may cause a motorvehicle accident. For rudimentary applications, a pedestrian collisionwarning signal may be automatically broadcast via the IES system 30 eachtime a user 11 is approaching an intersection 13 at the same time as amotor vehicle 32, irrespective of secondary variables. As seen, forexample, in FIG. 4, a wireless transmitter node 86 of the IES system 30may broadcast a pedestrian collision warning signal to a first user 11Awearing IES 10 who is approaching and predicted to cross a roadwayintersection 13A at the same time that a moving vehicle 32A is expectedto cross through the intersection 13A. Even though visually obstructedfrom each other by a building, a second user 11B wearing IES 10 andapproaching the intersection 13A at the same time as vehicle 32A mayalso receive a pedestrian collision warning signal. A pair of IES 10 maybe registered to a visually, physically or mentally impaired user 11C; apedestrian collision warning signal may also be sent to the third user11C due to the increased likelihood that this individual may unknowinglywander into the intersection 13A as the vehicle 32A is passing through.This warning signal may be sent to multiple users 11A, 11B, 11C and anypotentially threatening vehicle 32A such that each party can takeremediating action to prevent an inadvertent collision between apedestrian and an automobile.

For more sophisticated multimodal applications, the IES system 30receives data from an assortment of sensing devices that use, forexample, photo detection, radar, laser, ultrasonic, optical, infrared,damped mass, smart material, or other suitable technology for objectdetection and tracking. In accord with the illustrated example, the IESsystem 30 may be equipped with or receive sensor signals from one ormore digital cameras, one or more range sensors, one or more speedsensors, one or more dynamics sensors, and any requisite filtering,classification, fusion and analysis hardware and software for processingraw sensor data. Each sensor generates electrical signals indicative ofa characteristic or condition of a targeted object, generally as anestimate with a corresponding standard deviation. While the operatingcharacteristics of these sensors are generally complementary, some aremore reliable in estimating certain parameters than others. Most sensorshave different operating ranges and areas of coverage, and are capableof detecting different parameters within their operating range. Further,the performance of many sensor technologies may be affected by differingenvironmental conditions. Consequently, sensors generally presentparametric variances whose operative overlap offer opportunities forsensory fusion.

A dedicated control module or suitably programmed processor willaggregate and pre-process a collection of sensor-based data, fuse theaggregated data, analyze the fused data in conjunction with relatedcrowd-sourced data and behavioral data for each target object underevaluation, and estimate whether or not it is statistically probablethat a target object will enter a predicted path of a motor vehicle. Atinput/output block 109, for example, the resident footwear controller 44collects and transmits to the IES system 30: (1) position dataindicative of a real-time position of the IES 10 and, thus, the user 11,(2) dynamics data indicative of a real-time speed,acceleration/deceleration, and heading of the IES 10 and, thus, the user11, and (3) behavioral data indicative of historical behavior of theuser 11 while wearing IES 10. Such historical data may include pasttendencies of a given user when at a particular intersection or in aparticular geographic location, past tendencies of a given user in urbanor rural environments generally, past tendencies of a given user invarious weather conditions, past tendencies of a given user in specificdynamic scenarios, etc. It is envisioned that the IES controller 44 maycollect and transmit other types of data, including predictive path dataindicative of an estimated path for the user 11 based on availablecurrent and historical information.

At predefined process block 111, the method 100 of FIG. 5 proceeds withprocessor-executable instructions for a resident or remote controller toapply a sensor fusion module to aggregated raw sensor data to therebydetermine a likelihood of intrusion of a target object with respect tothe predicted route and location of a vehicle. IES system 30, forexample, conditions the data received from the resident footwearcontroller 44 in order to interrelate received sensor data to ensureoverlap with a single, common “reference” timeframe, coordinate system,set of standard measurements, etc. Once the received sensor data issufficiently conditioned to ensure alignment across related metrics, IESsystem 30 may execute a data association protocol that will classifyeach respective portion of sensor data, and then correlate relatedportions of sensor data based on any complementary classifications. IESsystem 30 may then execute a sensor fusion procedure of the conditionedand classified data along with path plan data of the target object andsubject vehicle. Sensor fusion may be typified as a computationalframework for the aggregation, analysis and alliance of data thatoriginates from heterogeneous or homogeneous sources (e.g., the multipledistinct sensor types discussed above). For the illustrated application,sensor fusion may be embodied as a dedicated software appliance thatintelligently combines data from several sensors and corrects for thedeficiencies of the individual sensors to calculate completely accurateand intelligible position and orientation information.

Upon completion of sensor fusion, the IES system 30 calculates apedestrian collision threat value. This collision threat value isprognosticative of a monitored target object behaving in a manner thatwill more likely than not cause a detrimental event. In accord with theillustrated example, a pedestrian collision threat value may bepredictive of intrusion of the user 11 in a manner that will at leastpartially obstruct a predicted route of the subject vehicle 32 as itrelates to a current (real-time) location of the subject vehicle. Thispedestrian collision threat value may be based on fusion of userposition data, user dynamics data, and user behavioral data. Optionally,a pedestrian collision threat value may also incorporate fusion of thebehavioral, user position, and user dynamics data with crowd-sourceddata and environmental data. Environmental data may be composed ofinformation that is indicative of a surrounding environment of the user,such as current weather conditions, current vehicle traffic conditions,current pedestrian traffic conditions, and the like. By comparison,crowd-sourced data may be composed of information that is indicative oflocation, movement and/or behavior of multiple individuals in proximityto the user. The remote computing node receiving the foregoing data mayinclude the remote host system 34, the cloud computing system 36, aresident vehicle controller 76 of the motor vehicle 32, or a distributedcomputing combination thereof. Alternatively, the footwear controller 44may transmit any or all of the foregoing data through a wirelesscommunications device 48, 50 to a central control unit of an intelligenttraffic management system.

Method 100 of FIG. 5 proceeds to decision block 113 to determine if thepedestrian collision threat value is greater than a calibrated thresholdvalue. A calibrated threshold value may be determined through empiricaltesting that provides sufficient quantitative data to establish astatistically significant minimum confidence percentage (e.g., 80%)below which a calculated collision threat value is either inconclusiveor probabilistically concludes a collision event will not occur.Responsive to a determination that the pedestrian collision threat valueis not greater than the calibrated threshold value (block 113=NO), themethod 100 may circle back to terminal block 101 and run in a continuousloop, or may proceed to terminal block 117 and temporarily terminate.Conversely, upon determining that the pedestrian collision threat valueis in fact greater than the calibrated threshold value (block 113=YES),the method 100 proceeds to process block 115 whereat one or moreremediating actions are taken to avoid a collision between a user and avehicle. By way of example, and not limitation, wireless transmitternode 86 may transmit a pedestrian collision imminent notification to thevehicle controller 76; vehicle controller 76 may immediately respond byissuing a braking command signal or signals to the vehicle brake systemto execute a braking maneuver, e.g., to come to a full stop or to reducespeed to a calculated value that will readily allow an evasive steeringmaneuver. In addition, or alternatively, the vehicle 32 may performother autonomous vehicle functions, such as controlling vehiclesteering, governing operation of the vehicle's transmission, controllingengine throttle, and other automated driving functions. Upon completionof the remediating actions executed at process block 115, the method 100proceeds to terminal block 117 and temporarily terminates.

In addition to facilitating automation of one or more vehicle operationsdesigned to mitigate or prevent a vehicle-pedestrian collision, method100 may concomitantly facilitate automation of one or more IES featuresdesigned to mitigate or prevent a vehicle-pedestrian collision atprocess block 115. For instance, a first command signal may betransmitted to a first IES subsystem to execute a first automatedfeature AF₁ of an intelligent electronic shoe. According to theillustrated example of FIG. 3, resident footwear controller 44 receivesthe pedestrian collision threat value output at block 111, establishesthat the threat value is greater than the threshold value at block 113,and responsively takes preventative action at block 115. Residentfootwear controller 44 automatically responds to this determination(i.e., without any user or external system prompt) by transmitting acommand signal to resident lighting system 56 to activate lightingdevice 58 to thereby generate a predetermined light output. The selectedcolor and/or pattern is detectable by the user 11 and, optionally, thedriver of vehicle 32, and is prominent enough to warn of the imminentcollision. By way of non-limiting example, resident lighting system 56may output a flashing, bright red-light pattern; use of this particularcolor and pattern may be restricted to warning the user of potentialdangers. Light output of the IES 10 may be coordinated with light outputof the forward-facing headlamps of the motor vehicle 32 to furtherfacilitate notifying the user 11 of a predicted vehicle collision.

It is envisioned that any of the disclosed connected wearable electronicdevices may automate additional or alternative features as part of themethodology 100 set forth in FIG. 5. Responding to a positivedetermination at decision block 113, footwear controller 44 mayautomatically transmit a second command signal to a second subsystem toexecute a second automated feature AF₂ of the wearable electronicdevice. As a non-limiting example, the IES 10 of FIG. 2 is shownequipped with a haptic transducer 66 that is housed inside the solestructure 14 in operative communication to the insole 22. To alert theuser 11 of the pedestrian collision threat assessment, the residentfootwear controller 44 emits a command signal to the haptic transducer66 to generate a haptic cue (e.g., a perceptible vibration force or aseries of vibration pulses) that is transmitted from the midsole 24,through the insole 22, and to the user's foot. The intensity and/orpulse pattern output by the haptic transducer 66 as part of method 100may be limited to instances of warning the user of a probable hazard.

An optional third automated feature AF₃ may include operating the lacemotor 64 as a tactile force-feedback device that is selectivelyactivated by the footwear controller 44 to rapidly tension and releasethe shoelace 20. Likewise, the IES 10 may operate in conjunction withthe smartphone 40 (e.g., coordinated flashing of an LED camera light oran eccentric rotating mass (ERM) actuator) or an active apparel element(e.g., coordinated activation of a thermal or haptic device built into ashirt or shorts). As yet another option, haptic feedback can be utilizedto provide turn-by-turn directions to the user (e.g., left foot or rightfoot vibrates at a heightened intensity and/or with a designated pulsepattern to indicate a left turn or right turn). In the same vein, hapticfeedback can be employed in a similar fashion to direct a user along apre-selected route or to warn a user against taking a particular route(e.g., deemed unsafe). Additional information regarding footwear andapparel with haptic feedback can be found, for example, in U.S. PatentApplication Publication No. 2017/0154505 A1, to Ernest Kim, which isincorporated herein by reference in its entirety and for all purposes.

Optionally, the IES 10 may be provided with an audio system, which isrepresented in FIG. 1 by a miniaturized audio speaker 68 that isattached to the rear quarter 12C of the upper 12. Resident footwearcontroller 44, upon confirming that the pedestrian collision threatvalue is greater than the calibrated threshold value, automaticallytransmits a command signal to the audio system speaker 68 to generate apredetermined sound output. For instance, the audio system speaker 68may blare “WARNING!” or “STOP!” at an increased sound level. As anotheroption, footwear controller 44 may command the lace motor 64 torepeatedly tighten/loosen the shoelace 20 as a signal/cue, e.g., of anoncoming automobile. Footwear-to-infrastructure communications may beenabled (and coordinated) to allow the IES 10 to communicate with anetworked “smart city” controller that, in turn, can modulate streetlighting or traffic light changes to improve safety for a walker orrunner. Conversely, the “smart city” controller may communicate with theIES 10 to warn the user they are coming up to a pedestrian crossing witha “Do Not Walk” sign signaling that pedestrians must yield the right ofway to oncoming vehicles.

Aspects of this disclosure may be implemented, in some embodiments,through a computer-executable program of instructions, such as programmodules, generally referred to as software applications or applicationprograms executed by any of the controller or controller variationsdescribed herein. Software may include, in non-limiting examples,routines, programs, objects, components, and data structures thatperform particular tasks or implement particular data types. Thesoftware may form an interface to allow a computer to react according toa source of input. The software may also cooperate with other codesegments to initiate a variety of tasks in response to data received inconjunction with the source of the received data. The software may bestored on any of a variety of memory media, such as CD-ROM, magneticdisk, bubble memory, and semiconductor memory (e.g., various types ofRAM or ROM).

Moreover, aspects of the present disclosure may be practiced with avariety of computer-system and computer-network configurations,including multiprocessor systems, microprocessor-based orprogrammable-consumer electronics, minicomputers, mainframe computers,and the like. In addition, aspects of the present disclosure may bepracticed in distributed-computing environments where tasks areperformed by remote-processing devices that are linked through acommunications network. In a distributed-computing environment, programmodules may be located in both local and remote computer-storage mediaincluding memory storage devices. Aspects of the present disclosure maytherefore be implemented in connection with various hardware, softwareor a combination thereof, in a computer system or other processingsystem.

Any of the methods described herein may include machine readableinstructions for execution by: (a) a processor, (b) a controller, and/or(c) any other suitable processing device. Any algorithm, software,protocol or method disclosed herein may be embodied as software storedon a tangible medium such as, for example, a flash memory, a CD-ROM, afloppy disk, a hard drive, a digital versatile disk (DVD), or othermemory devices. Persons of ordinary skill will readily appreciate thatthe entire algorithm and/or parts thereof could alternatively beexecuted by a device other than a controller and/or embodied in firmwareor dedicated hardware in an available manner (e.g., implemented by anapplication specific integrated circuit (ASIC), a programmable logicdevice (PLD), a field programmable logic device (FPLD), discrete logic,etc.). Further, although specific algorithms are described withreference to flowcharts depicted herein, many other methods ofimplementing the example machine readable instructions may alternativelybe used.

Aspects of the present disclosure have been described in detail withreference to the illustrated embodiments; those skilled in the art willrecognize, however, that many modifications may be made thereto withoutdeparting from the scope of the present disclosure. The presentdisclosure is not limited to the precise construction and compositionsdisclosed herein; any and all modifications, changes, and variationsapparent from the foregoing descriptions are within the scope of thedisclosure as defined by the appended claims. Moreover, the presentconcepts expressly include any and all combinations and subcombinationsof the preceding elements and features.

What is claimed:
 1. An Internet of Adaptive Apparel and Footwear (IoAAF)system for preventing a collision between a user and a machine moving ina building, the user having a portable electronic device with wirelesscommunications capabilities, the IoAAF system comprising: an article offootwear or apparel configured to be worn by the user; a collisionthreat warning system mounted to the footwear or apparel and configuredto generate visible, audible, and/or tactile outputs in response tocommand signals; a detection tag mounted to the footwear or apparel, thedetection tag being configured to receive a prompt signal from atransmitter-detector module affixed to or located within the buildingand responsively transmit to the transmitter-detector module a responsesignal indicative of a location of the user; a wireless communicationsdevice mounted to the footwear or apparel, the wireless communicationsdevice configured to wirelessly connect to the portable electronicdevice and thereby wirelessly communicate with a remote computing node;and an electronic controller device connected to the wirelesscommunications device and the collision threat warning system, theelectronic controller device being configured to: receive, from theremote computing node via the wireless communications device, acollision warning signal generated responsive to the response signalindicating the location of the user is within a predetermined proximityor location to the moving machine; and transmit, in response to thereceived collision warning signal, a command signal to the collisionthreat warning system to generate a predetermined visible, audible,and/or tactile alert configured to warn the user of an impendingcollision with the moving machine.
 2. The IoAAF system of claim 1,wherein the detection tag includes a radio frequency (RF) transponder,the prompt signal has a first RF power with a first frequency, and theresponse signal has a second RF power with a second frequency distinctfrom the first frequency.
 3. The IoAAF system of claim 2, wherein theprompt signal received from the transmitter-detector module includes anembedded data set, and wherein the response signal retransmits theembedded data set back to the transmitter-detector module.
 4. The IoAAFsystem of claim 3, wherein the RF transponder includes an RF antenna anda frequency filter connected to the RF antenna, the frequency filterbeing configured to reject signals having an RF power with a thirdfrequency distinct from the first frequency.
 5. The IoAAF system ofclaim 1, wherein the electronic controller device is further configuredto: transmit, to the remote computing node via the wirelesscommunications device, user dynamics data of the user; and receive, fromthe remote computing node via the wireless communications device, acollision threat value based on the user location and dynamics data andpredictive of intrusion of the user with respect to the location and apredicted route of the moving machine.
 6. The IoAAF system of claim 5,wherein the electronic controller device is further configured totransmit, to the remote computing node via the wireless communicationsdevice, behavioral data indicative of historical behavior of the user,wherein the collision threat value is further based on fusion of thebehavioral data with the user location and dynamics data.
 7. The IoAAFsystem of claim 6, wherein the collision threat value is further basedon fusion of the behavioral data, user location, and user dynamics datawith crowd-sourced data indicative of behavior of multiple users inproximity to the user.
 8. The IoAAF system of claim 7, wherein thecollision threat value is further based on fusion of the behavioraldata, user location, user dynamics data, and crowd-sourced data withenvironmental data indicative of a surrounding environment of the user.9. The IoAAF system of claim 1, wherein the wireless communicationsdevice includes a BLUETOOTH component or a near-field communications(NFC) component configured to wirelessly connect to the portableelectronic device.
 10. The IoAAF system of claim 1, wherein thecollision threat warning system includes a haptic transducer attached tothe footwear or apparel, and wherein the command signal causes thehaptic transducer to generate a predetermined tactile alert configuredto warn the user of the impending collision with the moving machine. 11.The IoAAF system of claim 1, wherein the collision threat warning systemincludes an audio component attached to the footwear or apparel, andwherein the command signal causes the audio component to generate apredetermined audible alert configured to warn the user of the impendingcollision with the moving machine.
 12. The IoAAF system of claim 1,wherein the collision threat warning system includes a lighting elementattached to the footwear or apparel, and wherein the command signalcauses the lighting element to generate a predetermined visible alertconfigured to warn the user of the impending collision with the movingmachine.
 13. The IoAAF system of claim 1, further comprising a pressuresensor mounted to a sole structure of the footwear and configured todetect a presence of a foot of the user in an upper of the footwear, andwherein the command signal is transmitted to the collision threatwarning system further in response to the detected presence of the footin the upper.
 14. The IoAAF system of claim 1, further comprising: ashoelace attached to an upper of the footwear; and a lace motor mountedinside a sole structure of the footwear and configured to selectivelytransition the shoelace between a tensioned state and an untensionedstate, wherein the electronic controller device is further configured tocommunicate with the lace motor and determine if the shoelace is in thetensioned state, and wherein the command signal is transmitted to thecollision threat warning system further in response to the shoelacebeing in the tensioned state.
 15. A method of operating an Internet ofAdaptive Apparel and Footwear (IoAAF) system for preventing a collisionbetween a user and a machine moving in a building, the user having aportable electronic device with wireless communications capabilities,the method comprising: receiving, via a detection tag attached to anarticle of footwear or apparel, a prompt signal from atransmitter-detector module affixed to or located within the building;transmitting, via the detection tag to the transmitter-detector moduleresponsive to receiving the prompt signal, a response signal indicativeof a location of the user; receiving, via an electronic controllerdevice through a wireless communications device attached to the footwearor apparel, a collision warning signal generated by a remote computingnode responsive to the response signal indicating the location of theuser is within a predetermined proximity or location to the movingmachine, wherein the wireless communications device wirelessly connectsto the portable electronic device and thereby wirelessly communicateswith the remote computing node; and transmitting, via the electroniccontroller device responsive to the received collision warning signal, acommand signal to a collision threat warning system attached to thefootwear or apparel to generate a predetermined visible, audible, and/ortactile alert configured to warn the user of an impending collision withthe moving machine.
 16. The method of claim 15, wherein the detectiontag includes a radio frequency (RF) transponder, the prompt signal has afirst RF power with a first frequency, and the response signal has asecond RF power with a second frequency distinct from the firstfrequency.
 17. The method of claim 15, further comprising: transmitting,via the electronic controller device to the remote computing node, userdynamics data of the user; and receiving, via the electronic controllerdevice through the wireless communications device from the remotecomputing node, a collision threat value based on the user location anddynamics data and predictive of intrusion of the user with respect tothe location and a predicted route of the moving machine.
 18. The methodof claim 15, further comprising detecting, via a pressure sensor mountedto the footwear, a presence of a foot in the footwear, and wherein thecommand signal is transmitted to the collision threat warning systemfurther in response to the detected presence of the foot in thefootwear.
 19. The method of claim 15, wherein the moving machine is arobot, a motor vehicle, a forklift, and/or an automated guided vehicle(AGV), and wherein the building is a manufacturing facility and/or astorage facility.
 20. An Internet of Adaptive Apparel and Footwear(IoAAF) system for preventing a collision between a user and a machinemoving in a building, the IoAAF system comprising: an article offootwear or apparel configured to be worn by the user; a collisionthreat warning system mounted to the footwear or apparel and configuredto generate visible, audible, and/or tactile outputs in response tocommand signals; a detection tag mounted to the footwear or apparel, thedetection tag being configured to receive a prompt signal from atransmitter-detector module affixed to or located within the buildingand responsively transmit to the transmitter-detector module a responsesignal indicative of a location of the user; a wireless communicationsdevice mounted to the footwear or apparel and configured to wirelesslycommunicate with a remote computing node; and an electronic controllerdevice connected to the wireless communications device and the collisionthreat warning system, the electronic controller device being configuredto: transmit, to the remote computing node via the wirelesscommunications device, user dynamics data and/or historical behavioraldata of the user; receive, from the remote computing node, a collisionwarning signal generated responsive to the response signal indicatingthe location of the user is within a predetermined proximity or locationto the moving machine; receive, from the remote computing node, acollision threat value based on fusion of the user location, userdynamics data, and/or historical behavioral data with crowd-sourced dataindicative of behavior of users in proximity to the user, the collisionthreat value being predictive of intrusion of the user with respect tothe location and a predicted route of the moving machine; and transmit,in response to the received collision warning signal, a command signalto the collision threat warning system to generate a predeterminedvisible, audible, and/or tactile alert configured to warn the user of animpending collision with the moving machine.